`unreachable!()`*should*bepresentinproductioncode

This is just a wording suggestion:

https://github.com/rust-lang/rust-clippy/blob/8325d48d2de179490eba9e682ffaaea375d2e1c9/clippy_lints/src/panic_unimplemented.rs#L69

is too strong of a claim. While it is reasonable to argue that

and

should not be present,

is a perfectly normal and preferred way to signal a dynamically unreachable code path, that can be improved only perhaps by adding a message. In particular, both

and other error handling via Result is not an appropriate substitute.

Since this is a

lint which is

by default it probably doesn't need to change triggering behavior, but I suggest changing the wording to be more neutral, like the

version:

该提问来源于开源项目：rust-lang/rust-clippy